Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update zerocracy/judges-action action to v0.0.50 - autoclosed #3351

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 27, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
zerocracy/judges-action action patch 0.0.49 -> 0.0.50

Release Notes

zerocracy/judges-action (zerocracy/judges-action)

v0.0.50: "workflow not found" error

Compare Source

See #​311, release log:

Released by Rultor 2.0-SNAPSHOT, see build log


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.


PR-Codex overview

This PR updates the zerocracy/judges-action to version 0.0.50 in the .github/workflows/zerocracy.yml.

Detailed summary

  • Updated zerocracy/judges-action to version 0.0.50.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@@ -32,7 +32,7 @@ jobs:
runs-on: ubuntu-22.04
steps:
- uses: actions/checkout@v4
- uses: zerocracy/[email protected].49
- uses: zerocracy/[email protected].50
with:
token: ${{ secrets.ZEROCRACY_TOKEN }}
options: |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code diff appears to be from a GitHub Actions YAML file, and the only difference is the version number of the zerocracy/judges-action being used. It changed from 0.0.49 to 0.0.50. This indicates an upgrade or change in the specific version of this action.

There are no obvious confusions or irregularities present given your input. However, you need to make sure that version 0.0.50 exists and doesn't introduce any breaking changes considering the context of how the action is being used in your workflow. If the new version introduces changes that aren't compatible with your existing setup, you might run into problems at runtime. It's also important to ensure that the ZEROCRACY_TOKEN secret is correctly set up in your GitHub repository settings so that the authentication doesn't fail.

@renovate renovate bot changed the title chore(deps): update zerocracy/judges-action action to v0.0.50 chore(deps): update zerocracy/judges-action action to v0.0.50 - autoclosed Aug 27, 2024
@renovate renovate bot closed this Aug 27, 2024
@renovate renovate bot deleted the renovate/zerocracy-judges-action-0.x branch August 27, 2024 06:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants